Jekyll is a great, fast alternative to a traditional CMS for developers
At my organization, we currently use Jekyll on my team as an easy way to publish our style guide and pattern library. The Jekyll site gets …
Overview
What is Jekyll?
Jekyll is an open source static site generator useful as a blog publishing system.
Recent Reviews
Pricing
N/A
Unavailable
What is Jekyll?
Jekyll is an open source static site generator useful as a blog publishing system.
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
3 people also want pricing
Alternatives Pricing
What is Duda?
Duda, the eponymous platform from the company in Palo Alto, is a web design platform for companies that offer web design services to small businesses. The company serves customers from freelance web professionals to digital agencies, all the way up to the large hosting companies, SaaS platforms and…
What is Prezly?
Prezly is presented as all-in-one public relations management tool that helps PR teams organise their workflow, collaborate and save time.Accessible through any browser, Prezly's key features are divided between three main areas: Contact managementFull PR CRM for managing contacts Automated contact…
Product Details
- About
- Tech Details
What is Jekyll?
Jekyll Technical Details
| Operating Systems | Unspecified |
|---|---|
| Mobile Application | No |
Comparisons
Compare with
Reviews and Ratings
(9)Reviews
(1-3 of 3)Companies can't remove reviews or game the system. Here's why
At my organization, we currently use Jekyll on my team as an easy way to publish our style guide and pattern library. The Jekyll site gets deployed automatically through GitHub pages. I use Jekyll personally for a portfolio website, also deployed through GitHub Pages. I also have used Netlify for publishing Jekyll sites in the past.
- Content stored in Git with the website code
- Free to use
- Easy to deploy to cheap/free hosting solutions
- Produces super fast static websites
- Not easy to update for non-developers
- No server-side language to support things like contact forms, so 3rd party software/service is needed
- Ruby gems can get messy
- It's free with GitHub Pages, so it cost us nothing to use
- It's tied into GitHub, so deploying changes is super easy (as opposed to deploying elsewhere)
- Keeps all content together with the code, so only one place to maintain information
The big alternatives to Jekyll are of course things like WordPress or Drupal, but they are almost something completely different: a full-blown CMS with a backend language and a database. Jekyll loses some of the niceties of these CMS solutions, like easily updating content from a user interface, but Jekyll will have much better performance by not having to render pages server-side or get content from a database.
I've also looked into (but not tried) several other Jekyll alternatives, such as Hugo, Middleman, and Pelican. Ultimately I decided on Jekyll because of it's ease of use with GitHub.
I've also looked into (but not tried) several other Jekyll alternatives, such as Hugo, Middleman, and Pelican. Ultimately I decided on Jekyll because of it's ease of use with GitHub.
January 17, 2018
Simple yet powerful CMS with Jekyll
We use Jekyll as a basic content management system framework for building basic, static, (and mostly freely hosted) websites. Generally the websites are either small prototypes, landing pages for new products or something new we're launching, or even as a basic blogging platform for one of our community driven technology sites. Jekyll helps you get up and running very quickly with a bare bones blog enabled site.
- Lightweight blogging framework
- Lots of support documentation
- Can host practically anywhere
- Complicated for non-technical users
- Can be difficult to enter in new content
- Implementing dynamic components can be challenging
- Jekyll has improved our time to market in cases of new projects
- Jekyll has reduced the cost of hosting a website
Jekyll has a much lower technical overhead in terms of server and hosting requirements to launch a site, but at the same time has a much more technical "interface" and doesn't have the dynamic capability, user management, or permission system as a standard CMS like Drupal or WordPress already has baked in.
August 03, 2017
Efficient Static Site Generation
Jekyll is used as the static site generator for project documentation, user guides, and developer best practices explanations. We're using it both through GitHub's built-in Pages feature (which compiles Jekyll sites for us automatically) and locally for content and design staging before anything ever ships to production. Jekyll allows us to work on the content of a documentation site independent of the code that builds and hosts the content.
- Static site generation
- Dynamic templates
- Single-page applications
- Advanced, multi-page navigation and organization with template hierarchy
- Ease of local usage (Ruby isn't always the friendliest environment, especially on Windows)
- Up-to-date documentation on configuration for edge cases and plugins
- All of our documentation is now centralized to one, version controlled location and presented seamlessly. Engineers don't have to spend hours trolling through a wiki or sorting Google Pages to find the information they need.
- Because Jekyll sites are fully-fledged websites, sometimes the _design_ of a document can overwhelm the interest of the team maintaining it - they'll spend more time perfecting the look/feel than they should.
Jekyll is integrated into GitHub Pages, which made it an easy choice. Using Jekyll was also easier as there's not really a server or a database to configure and you can just get things started from day one. Running and verifying content changes locally for developers is super efficient as Jekyll runs locally, too.